Information transmission method and apparatus

ABSTRACT

This application discloses a communication system including a master base station and a secondary base station, both connecting with a terminal. In the communication system, the master base station sends a first message to the secondary base station for allocating transmission resources for one or more flows to be transmitted between the secondary base station and a terminal, wherein the first message carries one or both of: identification information of each flow to be transmitted, and information of a data radio bearer (DRB) associated with each flow to be transmitted, then the secondary base station may determine a mapping relationship between a DRB and an admitted flow according to the first message. Moreover, the master base station sends DRB configuration information to the terminal. Therefore, requirements of 5G communication systems for QoS management of information transmission in a dual connectivity scenario can be met.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of a U.S. application Ser. No.16/458,174, filed on Jun. 30, 2019, which claims priority toInternational Application No. PCT/CN2018/071511, filed on Jan. 5, 2018.The International Application claims priority to Chinese PatentApplication No. 201710008434.X, filed on Jan. 5, 2017. The disclosuresof the aforementioned patent applications are hereby incorporated byreference in their entireties.

TECHNICAL FIELD

This application relates to the field of communications, and inparticular, to an information transmission method and apparatus.

BACKGROUND

The quality of service (QoS) mechanism is a security mechanism of anetwork. A network device processes data with different priorities byusing the QoS mechanism, to help reducing problems such as networklatency and network congestion.

In a Long Term Evolution (LTE) system, a core network device mapsdifferent flows to evolved packet system (EPS) bearers. One EPS bearerincludes one S1 bearer and one data radio bearer (DRB). The core networkdevice communicates with a base station by using the S1 bearer, and thebase station communicates with a terminal device by using the DRB. In adual connectivity (DC) scenario, when a master base station determinesto transfer a DRB to a secondary base station, the master base stationneeds to notify the core network device of an identifier of the DRB thatis to be transferred to the secondary base station, so that the corenetwork device may establish a transmission channel corresponding to theDRB with the secondary base station.

However, in a Fifth Generation (5G) communication system, higherrequirements on QoS management of data is imposed. In other words, morerefined QoS management needs to be performed on the data. In theexisting technology, DRB-based information transmission performedbetween the master base station and the secondary base station cannotmeet the requirements of the 5G communication system for QoS management.

SUMMARY

Embodiments of this application provide an information transmissionmethod and apparatus, to meet requirements of a 5G communication systemfor quality of service (QoS) management of information transmission in adual connectivity scenario.

According to a first aspect, an information transmission method isprovided. The method includes: sending, by a master base station, arequest message to a secondary base station, where the request messageincludes identification information of a flow, or the request messageincludes identification information of a flow and a mapping relationshipbetween the flow and a DRB; and receiving, by the master base stationfrom the secondary base station, a response message in response to therequest message.

According to the information transmission method provided in thisembodiment, the master base station sends, to the secondary basestation, identification information used to indicate at least one flow,or the master base station sends, to the secondary base station,identification information used to indicate at least one flow and amapping relationship between the at least one flow and one or more DRBs,so that the secondary base station can map flows to different DRBs basedon QoS requirements of the flows, thereby implementing QoS managementwith smaller granularity.

Optionally, the identification information of the flow includes a QoSmark of the flow.

According to the information transmission method provided in thisembodiment, the master base station uses the QoS mark of the flow as theidentification information of the flow, so that different flows can bedirectly distinguished, and QoS management with smaller granularity isimplemented.

Optionally, the identification information of the flow includes anidentifier of a protocol data unit (PDU) session to which the flowbelongs. Therefore, different flows can be distinguished, and QoSmanagement with smaller granularity is implemented.

Optionally, the request message further includes QoS characteristicinformation of the flow.

According to the information transmission method provided in thisembodiment, the master base station sends the QoS characteristicinformation of the flow to the secondary base station, so that thesecondary base station can determine a QoS requirement of the flow forthe DRB based on the QoS characteristic information of the flow.

Optionally, the request message further includes a DRB identifieravailable to the secondary base station.

According to the information transmission method provided in thisembodiment, the master base station sends, to the secondary basestation, the DRB identifier available to the secondary base station. Thesecondary base station may map the flow to the DRB based on the DRBidentifier available to the secondary base station, to avoid a conflictbetween a DRB mapped by the master base station and a DRB mapped by thesecondary base station, and reduce load of the master base station.

Optionally, the request message further includes a DRB identifierunavailable to the secondary base station.

The master base station may send, to the secondary base station, the DRBidentifier unavailable to the secondary base station. For example, themaster base station may send an identifier list of DRBs unavailable tothe flow to the secondary base station, to avoid a conflict between aDRB mapped by the master base station and a DRB mapped by the secondarybase station, and reduce load of the master base station.

Optionally, the response message includes identification information ofa flow admitted by the secondary base station and tunnel endpointinformation corresponding to the flow admitted by the secondary basestation.

Therefore, the master base station may determine, based on the responsemessage, a flow that can be split to the secondary base station.

Optionally, the response message includes identification information ofa flow that is not admitted by the secondary base station.

Therefore, the master base station may determine, based on the responsemessage, a flow that can be split to the secondary base station.

Optionally, the method further includes: sending, by the master basestation to a core network device, the identification information of theflow admitted by the secondary base station and the tunnel endpointinformation corresponding to the flow admitted by the secondary basestation; or sending, by the master base station to a core networkdevice, identification information of a flow admitted by the master basestation, tunnel endpoint information corresponding to the flow admittedby the master base station, the identification information of the flowadmitted by the secondary base station, and the tunnel endpointinformation corresponding to the flow admitted by the secondary basestation.

Both the flow admitted by the master base station and the flow admittedby the secondary base station are flows in a PDU session sent by a corenetwork to the master base station.

According to the information transmission method provided in thisembodiment, the base station sends, to the core network device, tunnelendpoint information corresponding to a flow included in the PDU sessionon the secondary base station, or the base station sends, to the corenetwork device, tunnel endpoint information corresponding to a flowincluded in the PDU session on the master base station and tunnelendpoint information corresponding to the flow included in the PDUsession on the secondary base station, so that a bearer can be createdor transferred based on flow information.

Optionally, the method further includes: sending, by the master basestation to a core network device, the identification information of theflow admitted by the secondary base station, the tunnel endpointinformation corresponding to the flow admitted by the secondary basestation, and an identifier of the secondary base station; or sending, bythe master base station to a core network device, identificationinformation of a flow admitted by the master base station, tunnelendpoint information corresponding to the flow admitted by the masterbase station, the identification information of the flow admitted by thesecondary base station, the tunnel endpoint information corresponding tothe flow admitted by the secondary base station, an identifier of themaster base station, and an identifier of the secondary base station.

Therefore, when flows in a PDU session are respectively carried bydifferent base stations, the core network device may determine, based onan identifier of a base station, a base station to which a flow in thePDU session is sent.

Optionally, the method further includes: sending, by the master basestation, DRB configuration information to user equipment, where the DRBconfiguration information includes a DRB identifier and identificationinformation of a flow corresponding to the DRB.

According to the information transmission method provided in thisembodiment, the user equipment may receive a flow from at least one ofthe master base station and the secondary base station based on the DRBconfiguration information, and a bearer can be created and transferredbased on flow information.

Optionally, before the sending, by a master base station, a requestmessage to a secondary base station, the method further includes:receiving, by the master base station, a flow identifier from the userequipment; and establishing, by the master base station, a bearer for aflow indicated by the flow identifier.

According to the information transmission method provided in thisembodiment, the base station establishes, based on the flow identifierreceived from the user equipment, the bearer for the flow indicated bythe flow identifier, so that a bearer can be created and transferredbased on flow information, and a requirement of a 5G communicationsystem for QoS management of information transmission can be met.

According to a second aspect, an information transmission method isprovided. The method includes: receiving, by a secondary base station, arequest message from a master base station, where the request messageincludes identification information of a flow, or the request messageincludes identification information of a flow and a mapping relationshipbetween the flow and a DRB; and sending, by the secondary base stationto the master base station, a response message in response to therequest message.

According to the information transmission method provided in thisembodiment, the secondary base station receives the identificationinformation of the flow sent by the master base station, to determine aQoS requirement of the flow based on the identification information ofthe flow, and map the flow to a DRB that meets the QoS requirement ofthe flow, thereby implementing more refined QoS management on data.

Optionally, the identification information of the flow includes aquality of service QoS mark of the flow.

Therefore, the secondary base station can directly distinguish betweendifferent flows, thereby implementing QoS management with smallergranularity.

Optionally, the identification information of the flow includes anidentifier of a PDU session to which the flow belongs.

Therefore, the secondary base station can distinguish between differentflows, thereby implementing QoS management with smaller granularity.

Optionally, the request message further includes QoS characteristicinformation of the flow.

Therefore, the secondary base station may determine the QoS requirementof the flow for the DRB based on the QoS characteristic information ofthe flow.

Optionally, the request message further includes a DRB identifieravailable to the secondary base station.

According to the information transmission method provided in thisembodiment, the master base station sends, to the secondary basestation, the DRB identifier available to the secondary base station. Thesecondary base station may map the flow to the DRB based on the DRBidentifier available to the secondary base station, to avoid a conflictbetween a DRB mapped by the master base station and a DRB mapped by thesecondary base station, and reduce load of the master base station.

Optionally, the request message further includes a DRB identifierunavailable to the secondary base station.

The master base station may send, to the secondary base station, the DRBidentifier unavailable to the secondary base station. For example, themaster base station may send an identifier list of DRBs unavailable tothe flow to the secondary base station, to avoid a conflict between aDRB mapped by the master base station and a DRB mapped by the secondarybase station, and reduce load of the master base station.

Optionally, the response message includes identification information ofa flow admitted by the secondary base station and tunnel endpointinformation corresponding to the flow admitted by the secondary basestation.

Therefore, the master base station may determine, based on the responsemessage, a flow that can be split to the secondary base station.

Optionally, the response message includes identification information ofa flow that is not admitted by the secondary base station.

Therefore, the master base station may determine, based on the responsemessage, a flow that can be split to the secondary base station.

According to a third aspect, an information transmission method isprovided. The method includes: receiving, by a core network device froma master base station, identification information of a flow admitted bya secondary base station and tunnel endpoint information correspondingto the flow admitted by the secondary base station; and sending, by thecore network device to the secondary base station based on the tunnelendpoint information corresponding to the flow admitted by the secondarybase station, the flow admitted by the secondary base station.

According to the information transmission method provided in thisembodiment, the core network device may send a flow to the secondarybase station based on tunnel endpoint information that is received fromthe master base station and that is corresponding to the flow migratedto the secondary base station on the secondary base station, so that abearer can be transferred based on flow information.

Optionally, the method further includes: receiving, by the core networkdevice, an identifier of the secondary base station from the master basestation.

Therefore, when flows in a PDU session are respectively carried bydifferent base stations, the core network device may determine, based onan identifier of a base station, a base station to which a flow in thePDU session is sent.

According to a fourth aspect, an information transmission method isprovided. The method includes: receiving, by a core network device froma master base station, identification information of a flow admitted bythe master base station, tunnel endpoint information corresponding tothe flow admitted by the master base station, identification informationof a flow admitted by a secondary base station, and tunnel endpointinformation corresponding to the flow admitted by the secondary basestation; sending, by the core network device to the master base stationbased on the tunnel endpoint information corresponding to the flowadmitted by the master base station, the flow admitted by the masterbase station; and sending, by the core network device to the secondarybase station based on the tunnel endpoint information corresponding tothe flow admitted by the secondary base station, the flow admitted bythe secondary base station.

According to the information transmission method provided in thisembodiment, flows may be sent to the master base station and thesecondary base station based on tunnel endpoint informationcorresponding to a flow on the master base station and tunnel endpointinformation corresponding to the flow on the secondary base station,where the two pieces of tunnel endpoint information are received fromthe master base station, so that a bearer can be created based on flowinformation.

Optionally, the method further includes: receiving, by the core networkdevice, an identifier of the master base station and an identifier ofthe secondary base station from the master base station.

Therefore, when flows in a PDU session are respectively carried bydifferent base stations, the core network device may determine, based onan identifier of a base station, a base station to which a flow in thePDU session is sent.

According to a fifth aspect, an information transmission method isprovided. The method includes: determining, by a user equipment device(UE), a first DRB based on identification information of first data; andsending, by the UE, the first data by using the first DRB.

According to the information transmission method provided in thisembodiment, the UE may determine a DRB that matches a QoS requirement ofuplink data, and a bearer can be created and transferred based on flowinformation.

Optionally, the determining, by UE, a first DRB based on identificationinformation of first data includes: determining, by the UE, that adefault bearer corresponding to an identifier of a PDU session is theDRB, where the identification information of the first data includes theidentifier of the PDU session.

According to the information transmission method provided in thisembodiment, the default bearer may be on a master base station, or maybe on a secondary base station. The UE may determine the DRB thatmatches the QoS requirement of the uplink data without exchanginginformation with another network element, so that signaling overheadscan be reduced.

Optionally, the determining, by the UE, a first DRB based onidentification information of first data includes: sending, by the UE, afirst request message to a base station, where the first request messageincludes identification information of the first data, and the firstrequest message is used to request the base station to perform DRBmapping for the first data; and receiving, by the UE, a reply messagefrom the base station, where the reply message includes a mappingrelationship between the first data and the first DRB.

Therefore, the UE may determine the DRB that matches the QoS requirementof the uplink data, and a bearer can be created and transferred based onflow information.

Optionally, the method further includes: determining, by the UE, theidentification information of the first data based on upper layerinformation and non-access stratum information.

Therefore, according to the information transmission method provided inthis embodiment, an access stratum of the UE determines identificationinformation of the uplink data based on the upper layer information andthe non-access stratum information, to determine, based on theidentification information of the uplink data, the DRB for sending theuplink data.

According to a sixth aspect, embodiments of this application provides aninformation transmission method, including: receiving, by a UE, aconfiguration message from a master base station, where theconfiguration message includes DRB configuration information on themaster base station and DRB configuration information on a secondarybase station, the DRB configuration information on the master basestation includes an identifier of a flow corresponding to a DRBestablished on the master base station, and the DRB configurationinformation on the secondary base station includes an identifier of aflow corresponding to a DRB established on the secondary base station;and sending, by the UE to the master base station, a response message inresponse to the configuration message.

Optionally, the response message is used to indicate that the UEcompletes configuration corresponding to the DRB configurationinformation on the master base station and configuration correspondingto the DRB configuration information on the secondary base station.

When a DRB needs to be established, the UE may receive data (namely, aflow) from at least one of the master base station and the secondarybase station based on DRB configuration information, and a bearer can becreated and transferred based on flow information.

Optionally, the configuration message is a radio resource control (RRC)connection reconfiguration message.

Optionally, the DRB configuration information on the master base stationfurther includes an identifier of a protocol data unit (PDU) session towhich the flow corresponding to the DRB established on the master basestation belongs, and/or the DRB configuration information on thesecondary base station further includes an identifier of a PDU sessionto which the flow corresponding to the DRB established on the secondarybase station belongs.

Optionally, the identifier of the PDU session to which the flowcorresponding to the DRB established on the master base station belongsis the same as the identifier of the PDU session to which the flowcorresponding to the DRB established on the secondary base stationbelongs.

Optionally, the method further includes: determining, by the UE, that aDRB corresponding to an identifier of a PDU session to which uplink databelongs is a default bearer, where the default bearer is established onthe master base station, or the default bearer is established on thesecondary base station.

According to a seventh aspect, an embodiment provides an informationtransmission apparatus. The apparatus can implement functions performedby the master base station in the method in the first aspect. Thefunctions may be implemented by using hardware, or may be implemented byhardware by executing corresponding software. The hardware or softwareincludes one or more units or modules corresponding to the functions.

In a possible design, a structure of the apparatus includes a processor,a communication interface, and a transceiver. The processor isconfigured to support the apparatus in performing a correspondingfunction in the foregoing method. The communication interface and thetransceiver are configured to support communication between theapparatus and another network element. The apparatus may further includea memory. The memory is coupled to the processor, and stores a programinstruction and data that are necessary to the apparatus.

According to an eighth aspect, an embodiment provides an informationtransmission apparatus. The apparatus can implement functions performedby the secondary base station in the method in the second aspect. Thefunctions may be implemented by using hardware, or may be implemented byhardware by executing corresponding software. The hardware or softwareincludes one or more units or modules corresponding to the functions.

In a possible design, a structure of the apparatus includes a processor,a communication interface, and a transceiver. The processor isconfigured to support the apparatus in performing a correspondingfunction in the foregoing method. The communication interface and thetransceiver are configured to support communication between theapparatus and another network element. The apparatus may further includea memory. The memory is coupled to the processor, and stores a programinstruction and data that are necessary to the apparatus.

According to a ninth aspect, an embodiment provides an informationtransmission apparatus. The apparatus can implement functions performedby the core network device in the method in the third aspect and/or thefourth aspect. The functions may be implemented by using hardware, ormay be implemented by hardware by executing corresponding software. Thehardware or software includes one or more units or modules correspondingto the functions.

In a possible design, a structure of the apparatus includes a processorand a communication interface. The processor is configured to supportthe apparatus in performing a corresponding function in the foregoingmethod. The communication interface is configured to supportcommunication between the apparatus and another network element. Theapparatus may further include a memory. The memory is coupled to theprocessor, and stores a program instruction and data that are necessaryto the apparatus.

According to a tenth aspect, an embodiment provides an informationtransmission apparatus. The apparatus can implement functions performedby the user equipment in the method in the fifth aspect and/or the sixthaspect. The functions may be implemented by using hardware, or may beimplemented by hardware by executing corresponding software. Thehardware or software includes one or more units or modules correspondingto the functions.

In a possible design, a structure of the apparatus includes a processorand a transceiver. The processor is configured to support the apparatusin performing a corresponding function in the foregoing method. Thetransceiver is configured to support communication between the apparatusand another network element. The apparatus may further include a memory.The memory is coupled to the processor, and stores a program instructionand data that are necessary to the apparatus.

According to an eleventh aspect, an embodiment provides a communicationsystem. The system includes the master base station and the secondarybase station that are described in the foregoing aspects. Optionally,the system may further include the core network device described in theforegoing aspects. Optionally, the system may further include the userequipment described in the foregoing aspects.

According to a twelfth aspect, an embodiment provides a computerreadable storage medium. The computer readable storage medium storescomputer program code, and when the computer program code is executed bya computer, the computer implements functions of the master base stationin the first aspect.

According to a thirteenth aspect, an embodiment provides a computerreadable storage medium. The computer readable storage medium storescomputer program code, and when the computer program code is executed bya computer, the computer implements functions of the secondary basestation in the second aspect.

According to a fourteenth aspect, an embodiment provides a computerreadable storage medium. The computer readable storage medium storescomputer program code, and when the computer program code is executed bya computer, the computer implements functions of the core network devicein the third aspect and/or the fourth aspect.

According to a fifteenth aspect, an embodiment provides a computerreadable storage medium. The computer readable storage medium storescomputer program code, and when the computer program code is executed bya computer, the computer implements functions of the terminal device inthe fifth aspect and/or the sixth aspect.

According to a sixteenth aspect, an embodiment provides a communicationchip system. The communication chip system includes at least oneprocessor, and the at least one processor is coupled to a memory, andreads and runs an instruction stored in the memory, to implementfunctions of the master base station in the first aspect.

According to a seventeenth aspect, an embodiment provides acommunication chip system. The communication chip system includes atleast one processor, and the at least one processor is coupled to amemory, and reads and runs an instruction stored in the memory, toimplement functions of the secondary base station in the second aspect.

According to an eighteenth aspect, an embodiment provides acommunication chip system. The communication chip system includes atleast one processor, and the at least one processor is coupled to amemory, and reads and runs an instruction stored in the memory, toimplement functions of the core network device in the third aspectand/or the fourth aspect.

According to a nineteenth aspect, an embodiment provides a communicationchip system. The communication chip system includes at least oneprocessor, and the at least one processor is coupled to a memory, andreads and runs an instruction stored in the memory, to implementfunctions of the terminal device in the fifth aspect and/or the sixthaspect.

According to a twentieth aspect, embodiments of this applicationprovides a computer program product. The computer program productincludes computer program code, and when the computer program code isrun by a master base station, the master base station performs themethod according to the first aspect.

According to a twenty-first aspect, embodiments of this applicationprovides a computer program product. The computer program productincludes computer program code, and when the computer program code isrun by a secondary base station, the secondary base station performs themethod according to the second aspect.

According to a twenty-second aspect, embodiments of this applicationprovides a computer program product. The computer program productincludes computer program code, and when the computer program code isrun by a core network device, the core network device performs themethod according to the third aspect and/or the fourth aspect.

According to a twenty-third aspect, embodiments of this applicationprovides a computer program product. The computer program productincludes computer program code, and when the computer program code isrun by a terminal device, the terminal device implements functions ofthe terminal device in the fifth aspect and/or the sixth aspect.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic architectural diagram of a communication system inwhich embodiments of the application may be applied;

FIG. 2 is a flowchart of an information transmission method according toan embodiment of this application;

FIG. 3 is a flowchart of an information transmission method according toanother embodiment of this application;

FIG. 4 is a flowchart of an information transmission method according toyet another embodiment of this application;

FIG. 5 is a flowchart of an information transmission method according tostill another embodiment of this application;

FIG. 6 is a schematic block diagram of a master base station accordingto an embodiment of this application;

FIG. 7 is a simplified structural diagram of a master base stationaccording to an embodiment of this application;

FIG. 8 is a block diagram of a secondary base station according to anembodiment of this application;

FIG. 9 is a simplified structural diagram of a secondary base stationaccording to an embodiment of this application;

FIG. 10 is a block diagram of a core network device according to anembodiment of this application;

FIG. 11 is a simplified structural diagram of a core network deviceaccording to an embodiment this application;

FIG. 12 is a block diagram of a user equipment device according to anembodiment this application; and

FIG. 13 is a simplified structural diagram of user equipment deviceaccording to an embodiment of this application.

DESCRIPTION OF EMBODIMENTS

The following describes technical solutions of this application withreference to accompanying drawings.

FIG. 1 shows a communication system in which embodiments of thisapplication may be applied. The communication system includes a corenetwork 110, a master base station 120, a secondary base station 130,and one or more user equipment device (referred as UE hereinafter) 140.The core network 110 separately communicates with the master basestation 120 and/or the secondary base station 130 through protocol dataunit (PDU) sessions. One PDU session may include a plurality of flows(as shown by lines in the figure). These flows may have a same QoSrequirement, or may have different QoS requirements. The core network110 provides a QoS requirement of a flow for the master base station 120and/or the secondary base station 130, and the master base station 120and/or the secondary base station 130 complete/completes mapping fromthe flow to a DRB. Correspondingly, flows included in one DRB have asame QoS requirement or similar QoS requirements.

When the master base station 120 determines to transfer some flows tothe secondary base station 130 for transmission, the master base station120 may send identification information of the flows to the secondarybase station 130. The secondary base station 130 may map the flows toDRBs that meet QoS requirements of the flows, thereby implementing morerefined QoS management on the flows.

In this application, the UE may communicate with one or more corenetwork devices by using a radio access network. The UE may be referredto by different names such as a terminal, an access terminal, a terminaldevice, a subscriber unit, a subscriber station, a mobile station, amobile console, a remote station, a remote terminal, a mobile device, auser terminal, a wireless communication device, a user agent, or a userapparatus. The access terminal may be a cellular phone, a cordlessphone, a session initiation protocol (SIP) phone, a wireless local loop(WLL) station, a personal digital assistant (PDA), a handheld devicewith wireless communication functions, a computing device or anotherprocessing device connected to a wireless modem, an in-vehicle device, awearable device, and user equipment in a 5G system. The 5G systemincludes, for example, a new radio (NR) system and an evolved LTE (eLTE)system. The eLTE system is an LTE system that is connected to a corenetwork of the 5G system, and the eLTE system supports newcharacteristics of the core network of the 5G system.

In this application, the master base station or the secondary basestation may be a base transceiver station (BTS) in a Code DivisionMultiple Address (CDMA) system, a NodeB (NB) in a Wideband Code DivisionMultiple Access (WCDMA) system, an evolved NodeB (eNB) in an LTE system,or a gNB in an NR system. The foregoing base stations are merelyexamples. The master base station or the secondary base station mayalternatively be a relay station, an access point, an in-vehicle device,a wearable device, or another type of device. For ease of description,in this application, apparatuses that provide the wireless communicationfunctions for the UE are collectively referred to as a base station.

In this application, a core network device may be a network element of anext generation core network (NGC), or may be a 5G core network (5G-CN)device, or may be another core network device. The NGC network elementmay include, for example, a control plane (CP) network element and auser plane (UP) network element. The core network device is not limitedin this application, and any core network device that can perform themethod described in the embodiments falls within the protection scope ofthis application. In addition, in this application, the “core networkdevice” is sometimes referred to as a “core network” for short.

The foregoing communication system is merely an example. Quantity ofcore networks and quantity of secondary base stations in a communicationsystem are not limited to the quantities shown in FIG. 1.

FIG. 2 is a flow diagram of an information transmission method accordingto an embodiment of the application. As shown in FIG. 2, the methodincludes the following steps.

S201. A master base station sends a request message to a secondary basestation, where the request message includes identification informationof a flow, or the request message includes identification information ofa flow plus a mapping relationship between the flow and a DRB.

S202. The master base station receives, from the secondary base station,a response message in response to the request message.

In this embodiment, when the master base station determines to transfera set of flows (which includes at least one flow) to the secondary basestation (for ease of description, the set of flows is referred to as a“first flow”), the master base station sends a request message to thesecondary base station. For example, the request message may be asecondary base station addition request message, and the request messageis used to request the secondary base station to allocate, to the firstflow, a resource used to transmit the first flow. For example, therequest message may be signaling, or may be a data packet.

The request message includes identification information of at least oneflow in the first flow, and the identification information of the atleast one flow in the first flow is used to identify the at least oneflow in the first flow. The secondary base station determines the firstflow based on the identification information. If the secondary basestation admits the first flow, the secondary base station may determinea mapping relationship between the first flow and one or more DRBs, sothat the secondary base station may map the at least one flow in thefirst flow to the DRBs.

Alternatively, in addition to the identification information of thefirst flow, the request message may further include a mappingrelationship between the first flow and one or more DRBs that isdetermined by the master base station. The secondary base stationdetermines the first flow based on the identification information of thefirst flow. If the secondary base station admits the first flow, thesecondary base station maps the first flow to one or more DRBs based onthe mapping relationship between the first flow and the DRBs.

In this application, when the first flow includes two or more flows, theat two or more flows may belong to a same PDU session, or may belong todifferent PDU sessions. The secondary base station may admit all flowsin the first flow, or may admit some flows in the first flow. A flowthat is admitted by the secondary base station may be a flow that issuccessfully established or modified by the secondary base station.Specifically, the flow may be a flow of a corresponding DRBconfiguration that is successfully established or modified by thesecondary base station.

According to the information transmission method provided in thisembodiment, the master base station sends, to the secondary basestation, identification information of one or more flows, or the masterbase station sends, to the secondary base station, identificationinformation of one or more flows and a mapping relationship between eachflow and a DRB. The secondary base station maps flows to different DRBsbased on QoS requirements of the flows, thereby implementing QoSmanagement with smaller granularity.

Optionally, the identification information of the first flow includesone or more QoS marks of the first flow.

The master base station may directly use the one or more QoS marks ofthe first flow to identify the one or more flows in the first flow.Alternatively, the master base station may map the QoS marks to theidentification information of one or more flows in the first flow, andin this case, the master base station further needs to notify thesecondary base station and the UE of a mapping relationship between theQoS marks and the identification information of one or more flows in thefirst flow. That the QoS marks are mapped to the identificationinformation of one or more flows in the first flow may be as follows:For example, indexes of received QoS marks are sorted in sequence, wherean index number of a QoS mark is an identifier of a flow in the firstflow. The foregoing method is merely an example for description. Thisembodiment is not limited thereto. Any method for identifying a flow inthe first flow based on a QoS mark of the flow falls within theprotection scope of this application.

According to the information transmission method provided in thisembodiment, the master base station uses the QoS marks of the first flowas the identification information of the first flow, so that differentflows in the first flow can be directly distinguished, and QoSmanagement with smaller granularity is implemented.

Optionally, the identification information of the first flow includesidentifiers of one or more PDU sessions to which the first flow belongs.

For example, when the first flow includes two flows that belong todifferent PDU sessions, and the two flows have a same QoS mark, themaster base station may separately map, to identifiers of the two flows,identifiers of the PDU sessions to which the two flows belong.Alternatively, the master base station may directly use the identifiersof the PDU sessions to which the two flows belong as the identificationinformation of the first flow. The master base station may also use theQoS mark of each of the two flows and the identifiers of the PDUsessions to which the two flows belong as the identification informationof the first flow. The master base station maps, to an identifier of aflow, the QoS mark of the two flows and an identifier of a PDU sessionto which the flow belongs. In this mapping case, the master base stationneeds to notify the secondary base station and the UE of the mappingrelationship. The foregoing method is merely an example for description.This embodiment is not limited thereto. Any method for identifying thefirst flow based on the identifier of the PDU session to which the firstflow belongs falls within the protection scope of this application.

Therefore, according to the information transmission method provided inthis embodiment, the master base station uses the identifier of the PDUsession to which the first flow belongs as the identificationinformation of the first flow. The master base station may also use theQoS marks of the first flow and the identifiers of the one or more PDUsessions to which the first flow belongs as the identificationinformation of the first flow, so that different flows can be directlydistinguished, and QoS management with smaller granularity isimplemented.

Optionally, the request message further includes QoS characteristicinformation of the first flow.

The QoS characteristic information includes at least one group of QoScharacteristics. One group of QoS characteristics is a specific QoSrequirement, and the QoS requirement may be, for example, a packet lossrate, a delay, and a priority. Each QoS mark is corresponding to onegroup of QoS characteristics.

According to the information transmission method provided in thisembodiment, the master base station sends the QoS characteristicinformation of the first flow to the secondary base station, so that thesecondary base station can determine a QoS requirement of the first flowfor one or more DRBs based on the QoS characteristic information of thefirst flow.

Optionally, the request message further includes one or more identifiersof DRBs available to the secondary base station.

In this embodiment, the master base station may determine one or moreDRBs to which the first flow is mapped, and indicate the mappingrelationship between the first flow and the DRBs to the secondary basestation by using indication information. The master base station may notperform mapping from the first flow to the DRBs, but indicates, to thesecondary base station, one or more DRB identifiers to which the firstflow can be mapped, and the secondary base station performs mapping fromthe first flow to the DRBs. For example, the master base station maysend, to the secondary base station, an identifier list of DRBsavailable to the first flow, and the secondary base station determinesidentifiers of to-be-used DRBs. The foregoing method is merely anexample for description. This embodiment is not limited thereto.

Therefore, according to the information transmission method provided inthis embodiment, the master base station sends, to the secondary basestation, one or more identifiers of DRBs available to the secondary basestation. The secondary base station may map the first flow to the DRBsbased on the one or more DRB identifiers available to the secondary basestation, to avoid a conflict between a DRB mapped by the master basestation and a DRB mapped by the secondary base station, and reduce loadof the master base station.

Optionally, the request message further includes one or more identifiersof DRBs unavailable to the secondary base station.

The master base station may send, to the secondary base station, theidentifiers of DRBs unavailable to the secondary base station. Forexample, the master base station may send, to the secondary basestation, an identifier list of DRBs unavailable to the first flow. Forexample, the master base station may indicate, to the secondary basestation, an identifier of a DRB that is used by the master base station,to avoid a conflict between a DRB mapped by the master base station anda DRB mapped by the secondary base station, and reduce load of themaster base station.

The foregoing method is merely an example for description. Thisembodiment is not limited thereto. For example, the master base stationmay further send, to the secondary base station, an identifier of a DRBthat is available to the first flow and an identifier of a DRB that isunavailable to the first flow. The two identifiers may be sent to thesecondary base station in two lists, or may be sent to the secondarybase station in one list, and identifiers of different types of DRBs inone list may be distinguished by using identifier bits.

The foregoing information included in the request message is merely anexample for description, and should not be regarded as a limitation onthis embodiment. The request message may further include otherinformation. For example, the request message may further include tunnelendpoint information of the PDU session to which the first flow belongson a core network node. The tunnel endpoint information may be a generalpacket radio service (GPRS) tunneling protocol (GTP) tunnel endpointidentifier (GTP-TEID) and a transport layer address, or may be tunnelendpoint information based on a power over Ethernet (PoE) protocol, ormay be tunnel endpoint information based on another transport layerprotocol. This is not limited in this embodiment.

In S202, after receiving the request message sent by the master basestation, the secondary base station performs configuration, and sends,to the master base station, the response message in response to therequest message (for example, the response message may be a secondarybase station addition request response message). The response messageindicates a result of processing performed by the secondary base stationon the first flow. For example, when the secondary base stationdetermines to reject the first flow, the response message may include abit indicating that the first flow is rejected, or the response messagemay include indication information used to indicate that a resourceallocated to the first flow is 0. When the secondary base stationdetermines to admit the first flow, the response message may indicate aresource allocated by the secondary base station to the first flow. Foranother example, the response message includes two lists. One listincludes information about a flow in the first flow that is admitted bythe secondary base station, and the other list includes informationabout a flow in the first flow that is rejected by the secondary basestation.

Optionally, the response message includes identification information ofa flow admitted by the secondary base station and tunnel endpointinformation corresponding to the flow admitted by the secondary basestation.

When the secondary base station determines to admit the first flow, ifthe secondary base station admits some flows in the first flow, theresponse message includes identification information of the admittedflows in the first flow and tunnel endpoint information corresponding tothe admitted flows. Optionally, if the secondary base station admits allflows in the first flow, the response message may indicate, according toone bit, that the secondary base station admits all the flows in thefirst flow, or may send identification information of the admitted flowsin the first flow to the master base station.

Therefore, the master base station may determine, based on the responsemessage, a flow that can be split to the secondary base station.

Optionally, the response message includes identification information ofa flow that is not admitted by the secondary base station.

If the secondary base station admits some flows in the first flow, theresponse message may include identification information of a flow thatis not admitted by the secondary base station in the first flow, so thatthe master base station can determine, based on the response message, aflow that can be split to the secondary base station. The foregoingmethod is merely an example for description. This embodiment is notlimited thereto. For example, the response message may include all theidentification information of the flow admitted by the secondary basestation, the tunnel endpoint information corresponding to the flowadmitted by the secondary base station, and the identificationinformation of the flow rejected by the secondary base station.

Information included in the response message is merely an example fordescription, and should not be regarded as a limitation on thisembodiment. The foregoing response message may further include otherinformation.

For example, the response message may further include tunnel endpointinformation of the PDU session to which the first flow belongs on thesecondary base station. The tunnel endpoint information may be aGTP-TEID and a transport layer address, or may be tunnel endpointinformation based on a PoE protocol, or may be tunnel endpointinformation based on another transport layer protocol. This is notlimited in this embodiment.

For another example, when the secondary base station determines themapping relationship between the first flow and one or more DRBs, theresponse message further includes indication information indicating themapping relationship.

For another example, when the master base station determines the mappingrelationship between the first flow and one or more DRBs, the responsemessage further includes information about an admitted DRB andinformation about a rejected DRB. Information about a DRB includes anidentifier of the DRB.

The response message may include all information described above, or mayinclude only a part of information described above.

Optionally, in an implementation of this embodiment, the method furtherincludes:

S203. The master base station sends, to a core network device,identification information of a flow admitted by the secondary basestation and tunnel endpoint information corresponding to the flowadmitted by the secondary base station.

Alternatively, the method further includes: S204. The master basestation sends, to a core network device, identification information of aflow admitted by the master base station, tunnel endpoint informationcorresponding to the flow admitted by the master base station,identification information of a flow admitted by the secondary basestation, and tunnel endpoint information corresponding to the flowadmitted by the secondary base station.

In this embodiment, the master base station sends, to the core networkdevice, tunnel endpoint information corresponding to flows admitted bybase stations (including the master base station and the secondary basestation) in flows included in a PDU session on the base stations. Thetunnel endpoint information corresponding to the base stations may becarried in a session setup reply message, or may be carried in a sessionmodification indication message.

S203 and S204 are two optional execution steps, in other words, themaster base station may perform S203 or S204.

When both tunnel endpoint information corresponding to the master basestation and tunnel endpoint information corresponding to the secondarybase station are carried in the session setup reply message, to bespecific, in a scenario in which S204 can be performed, the sessionsetup reply message is used to indicate a setup status of a PDU session.The session setup reply message includes at least one piece ofinformation about a PDU session that is successfully set up andinformation about a PDU session that is not successfully set up. Forexample, the information about the PDU session that is successfully setup includes an identifier of the PDU session, a QoS mark, and GTP-TEIDsand transport layer addresses of a flow identified by the QoS mark onthe base stations (including the master base station and the secondarybase station). Optionally, the session setup reply message furtherincludes identifiers of the base stations. Optionally, the session setupreply message may include only the identification information of theflow admitted by the secondary base station and the tunnel endpointinformation corresponding to the flow admitted by the secondary basestation.

When the tunnel endpoint information corresponding to the secondary basestation is carried in the session modification indication message, in ascenario in which S203 is performed, the session modification indicationmessage is used to instruct the core network device to migrate, to thesecondary base station, the flow admitted by the secondary base stationin the first flow. For example, the session modification indicationmessage includes a QoS mark, and a GTP-TEID and a transport layeraddress of a flow identified by the QoS mark on the secondary basestation. Optionally, the session modification indication message mayfurther include an identifier of a PDU session to which the flowidentified by the QoS mark belongs. If the entire PDU session ismigrated to the secondary base station, the session modificationindication message may include only the identifier of the PDU session,and a GTP-TEID and a transport layer address of the PDU session on thesecondary base station.

According to the information transmission method provided in thisembodiment, the base station sends, to the core network device, tunnelendpoint information corresponding to a flow included in the PDU sessionon the secondary base station. Alternatively, the base station sends, tothe core network device, tunnel endpoint information corresponding to aflow included in the PDU session on the master base station and tunnelendpoint information corresponding to the flow included in the PDUsession on the secondary base station. As a result, a bearer can becreated and transferred based on flow information.

Optionally, in an implementation of this embodiment, the method furtherincludes:

S205. The master base station sends DRB configuration information to aUE, where the DRB configuration information includes a DRB identifierand identification information of a flow corresponding to the DRB.

The DRB configuration information includes identification information ofa flow corresponding to each of DRBs respectively corresponding to themaster base station and the secondary base station, to be specific, theDRB configuration information indicates DRBs to be established on themaster base station and DRBs to be established on the secondary basestation.

After receiving the response message from the secondary base station, orafter sending the session setup reply message or the sessionmodification indication message to the core network, the master basestation sends a radio resource control (RRC) connection reconfigurationmessage to the UE. The RRC connection reconfiguration message includesthe foregoing DRB configuration information.

According to the information transmission method provided in thisembodiment, the UE may receive data (namely, a flow) from at least oneof the master base station and the secondary base station based on theDRB configuration information, and a bearer can be created andtransferred based on flow information.

Optionally, before the master base station sends the request message tothe secondary base station, the method further includes:

S206. The master base station receives a flow identifier from the UE.

S207. The master base station establishes, based on the flow identifier,a bearer for a flow indicated by the flow identifier.

The flow identifier is used to indicate the flow, and a specific form ofthe flow identifier is not limited in this application. When the UE hasto-be-uploaded data and cannot determine a mapping relationship betweena flow and a DRB, the UE may send a flow identifier corresponding to thedata to a base station (including the master base station or thesecondary base station). The base station performs mapping from a flowto a DRB for the flow indicated by the flow identifier. How the userequipment determines the flow identifier corresponding to the data isnot limited in this application.

In an optional implementation, the flow identifier may be carried in anRRC request message. After receiving the RRC request message, the basestation triggers an establishment process of the bearer corresponding tothe flow identifier. The bearer may be a bearer established only on themaster base station, or may be a bearer established only on thesecondary base station, or may be a split bearer established on both themaster base station and the secondary base station.

In another optional implementation, the flow identifier may be sent tothe base station together with uplink data. The base station triggers,based on a preset command in the base station, an establishment processof the bearer corresponding to the flow identifier. The bearer may be abearer on the master base station, or may be a bearer on the secondarybase station, or may be a split bearer.

When the base station determines to establish the bearer for the UE, thebase station may perform the foregoing processes of S201 and S202 andanother process used to establish a bearer for the UE in thisapplication. Details are not described herein again.

According to the information transmission method provided in thisembodiment, the base station establishes, based on the flow identifierreceived from the UE, the bearer for the flow indicated by the flowidentifier. Therefore, a bearer can be created and transferred based onflow information, and a requirement of a 5G communication system for QoSmanagement of information transmission can be met.

The information transmission method provided in this application isseparately described from a perspective of a base station, a corenetwork, and a terminal device in the foregoing embodiment. Thefollowing further describes the embodiments in detail based on a commonaspect of the embodiment described above.

FIG. 3 is a flowchart of an information transmission method according toanother embodiment of the application. As shown in FIG. 3, the methodincludes the following steps.

S301. An NGC sends a session setup request message to a master basestation, where the session setup request message carries at least onepiece of PDU session information. Specifically, the PDU sessioninformation includes an identifier of a PDU session, a GTP-TEID, atransport layer address, and a NAS-level QoS description, and theNAS-level QoS description includes a QoS characteristic and a QoS mark.The GTP tunnel endpoint identifier and the transport layer address areused to identify an endpoint of the PDU session at a core network nodeon a next generation (NextGen, NG) interface. In this case, informationelements included in the session setup request message may be shown inTable 1, or may be in another form. This is not limited in thisapplication.

TABLE 1  PDU session to be setup list >PDU session to be setup item IEs    >>PDU session ID   >>Transport Layer address      >>GTP-TEID >>NAS-level QoS profile item IEs      >>>QoS marking   >>>QoS characteristic

In Table 1, “PDU session to be setup list” indicates “a list of PDUsessions that are to be set up”. “PDU session to be setup item IEs”indicates “information elements included in the list of PDU sessionsthat are to be set up”. IE is short for information element. “PDUsession ID” indicates “an identifier of a PDU session”. ID is short foridentification, “Transport Layer address” indicates “a transport layerprotocol”. “GTP-TEID” indicates “a GTP tunnel endpoint identifier”.“NAS-level QoS profile item IEs” indicates “information elementsincluded in the NAS-level QoS description”. “QoS characteristic”indicates “a QoS characteristic”, and “QoS marking” indicates “a QoSmark”.

In Table 1, the NAS-level QoS description is used for QoS control, anddata packets marked with a same QoS mark have a same QoS requirement.For a base station, different QoS marks identify different flows. Inaddition, one PDU session may include a plurality of flows, and at leastone PDU session may be set up in one PUD session setup process.

S302. After receiving the session setup request message, the master basestation determines to transfer some or all flows corresponding to thesession setup request message to a secondary base station fortransmission (to be specific, the master base station makes a splitdecision). Optionally, the master base station may map the QoS mark toan identifier of a flow. Alternatively, the master base station maydirectly use the QoS mark to identify the flow, and in this case, anidentifier of the flow is the QoS mark. In this application, when both“an identifier of a flow” and “identification information of a flow” areused to indicate the flow, the two may be used interchangeably.

If the QoS mark is not unique between PDU sessions, to be specific, thePDU sessions may have the same QoS mark, a QoS mark of a flow and a PDUsession identifier of a PDU session to which the flow belongs may bemapped to an identifier of the flow. Alternatively, a QoS mark of a flowand a PDU session identifier of a PDU session to which the flow belongsare used to identify the flow, and in this case, an identifier of theflow is the QoS identifier and the PDU session identifier. In thisapplication, the identifier of the flow may be any one of the foregoingcases.

S303. The master base station sends a secondary base station additionrequest message to the secondary base station, where the message carriesat least one piece of flow information. The flow information may includea QoS mark of a flow, a QoS characteristic of the flow, a GTP tunnelidentifier and a transport layer address of a PDU session to which theflow belongs on a core network node, and optionally, may further includean identifier of the PDU session. In this case, a specific informationelement design may be described in Table 2 and Table 3, or may be inanother form. This is not limited in this application.

TABLE 2  PDU session to be split list >PDU session to be split item IEs    >>PDU session ID   >>Transport Layer address       >>GTP-TEID  >>Flow to be spit item IEs      >>>QoS marking    >>>QoScharacteristic

TABLE 3  Flow to be split list >flow to be split item IEs    >>QoSmarking  >>QoS characteristic   >>PDU session ID >>Transport Layeraddress     >>GTP-TEID

In Table 2, “PDU session to be split list” indicates “a list of PDUsessions to which split flows belong”, and “PDU session to be split itemIEs” indicates “information elements included in the list of PDUsessions to which split flows belong”. Meanings of remaining informationelements are shown in Table 1. Details are not described herein again.

In Table 3, “Flow to be split list” indicates “a list of to-be-splitflows”, and “flow to be split item IEs” indicates “information elementsincluded in the list of to-be-split flows”. Meanings of remaininginformation elements are shown in Table 1 and Table 2. Details are notdescribed herein again.

If the master base station performs mapping from the flow to a DRB, amapping relationship between the DRB and the flow is also carried in themessage. In this case, at least one flow may be mapped to one DRB, andthe at least one flow may belong to a same PDU session, or may belong todifferent PDU sessions. In this case, an information element design maybe shown in Table 4 to Table 6, or may be in another form. This is notlimited in this application. A PDU session identifier is optional.

TABLE 4    DRB to be split list  >DRB to be split item IEs       >>DRBID    >>PDU session ID >>Transport Layer address      >>GTP-TEID >>Flowto be spit item IEs     >>>QoS marking   >>>QoS characteristic

TABLE 5  DRB to be split list >DRB to be split item IEs       >>DRBID >>flow to be split item IEs     >>>QoS marking   >>>QoScharacteristic    >>>PDU session ID >>>Transport Layer address     >>>GTP-TEID

TABLE 6  DRB to be split list >DRB to be split item IEs      >>DRBID >>tunnel endpoint item Ws   >>>PDU session ID >>>Transport Layeraddress     >>>GTP-TEID    >>>QoS marking  >>>QoS characteristic

In Table 4, “DRB to be split list” indicates “a list of DRBscorresponding to split flows”, and “DRB to be split item IEs” indicates“information elements included in the list of DRBs corresponding tosplit flows”. “DRB ID” indicates “a DRB identifier”, and meanings ofremaining information elements are shown in Table 1 to Table 3. Detailsare not described herein again.

In Table 5, meanings of information elements are shown in Table 1 toTable 4. Details are not described herein again.

In Table 6, “tunnel endpoint item IEs” indicates “information elementsincluded in a tunnel endpoint”, and meanings of remaining informationelements are shown in Table 1 to Table 5. Details are not describedherein again.

If the master base station does not perform mapping from a flow to a DRBfor the flow to be split to the secondary base station, but thesecondary base station performs the mapping, in this case, to avoid aconflict occurs in DRBs, the master base station needs to send anindication to the secondary base station. The indication is used toindicate a DRB identifier that can be configured for the secondary basestation. Optionally, the indication information may be an identifierlist of DRBs configured on a master base station side, or may be anidentifier list of available DRBs allocated by the master base stationto the secondary base station, or may be another identifier list ofDRBs. This is not limited in this application.

S304. After receiving the request from the master base station, thesecondary base station performs configuration, and returns a secondarybase station request reply message to the master base station. If themaster base station does not add, to the request message, a DRBidentifier corresponding to the flow, the secondary base station requestreply message carries flow information of an admitted and split flow,and may further carry information about a rejected flow. Specifically,the flow information of the split flow admitted by the secondary basestation includes at least an identifier of the flow, and a GTP tunnelidentifier and a transport layer address of a PDU session in which theflow is located on the secondary base station. Optionally, the messagemay further include an identifier of the PDU session. A mappingrelationship between the flow and a DRB is determined by the secondarybase station, and the mapping relationship between the flow and the DRBmay also be carried in the message. The information about the flowrejected by the secondary base station includes at least an identifierof the flow.

If the master base station adds a mapping relationship between the flowand the DRB to the request message, the secondary base station addsinformation about a DRB corresponding to an admitted and split flow tothe message, and may further add information about a rejected DRB to themessage. Specifically, the information about the DRB corresponding tothe split flow admitted by the secondary base station may include anidentifier of the DRB. If flows in the DRB belong to only one PDUsession, the information about the DRB further includes a GTP tunnelidentifier and a transport layer address of the PDU session to which theflows in the DRB belong on the secondary base station. If flows in theDRB belong to different PDU sessions, the information about the DRBfurther includes an identifier of a flow, and a GTP tunnel identifierand a transport layer address of a PDU session in which the flow islocated on the secondary base station. The information about the DRBrejected by the secondary base station includes at least a DRB ID. Thesecondary base station may admit only some flows in the DRB, and in thiscase, the information about the rejected DRB further includes anidentifier of a rejected flow. Optionally, flow information of two listsmay further include an identifier of a PDU session.

S305. The master base station sends a session setup reply message to theNGC, where the message carries information about a PDU session that issuccessfully set up, and may further carry information about a PDUsession that is not successfully set up. Specifically, the informationabout the PDU session that is successfully set up includes an identifierof the PDU session, a QoS mark, and a GTP tunnel identifier and atransport layer address of the PDU session that carries a flowidentified by the QoS mark on a base station. The base station may bethe master base station, or may be the secondary base station.Optionally, the information about the PDU session that is successfullyset up may further include an identifier of the base station. In thiscase, an information element design may be shown in Table 7, or may bein another form. This is not limited in this application.

TABLE 7   PDU session setup list >PDU session setup item IEs    >>PDUsession ID  >>tunnel endpoint item IEs   >>>Transport layer address     >>>GTP-TEID     >>Flow item IEs     >>>QoS marking

In Table 7, “PDU session setup list” indicates “a list of PDU sessionsthat are set up”, “PDU session setup item IEs” indicates “informationelements included in the list of PDU sessions that are set up”, andmeanings of remaining information elements are shown in Table 1 to Table6. Details are not described herein again.

In this case, for one PDU session, a core network side may need tomaintain GTP tunnel identifiers and transport layer addresses of aplurality of base station sides.

The information about the PDU session that is not successfully set upincludes an identifier of the PDU session that is not successfully setup. In this case, in a PDU session, some flows may be successfullyadmitted by the master base station or the secondary base station, andsome other flows are not admitted. In this case, the PDU session that isnot successfully set up further needs to carry an identifier of aspecific flow that is not admitted. For a PDU session in which none offlows is admitted, there is no need to carry a flow identifier.

S306. The master base station sends an RRC connection reconfigurationmessage to UE. The RRC connection reconfiguration message carries DRBconfiguration information on the master base station and DRBconfiguration information on the secondary base station. Specifically,the DRB configuration information is used to indicate, to the UE, DRBsto be established on the master base station and DRBs to be establishedon the secondary base station. The configuration information includes atleast one of an identifier of a flow corresponding to each DRB and anidentifier of a PDU session to which the flow corresponding to each DRBbelongs. It should be noted that, in this case, if the identifier of theflow is not a QoS mark, a mapping relationship between the identifier ofthe flow and the QoS mark needs to be notified to the UE. There is nosequence between S306 and S305.

S307. After completing configuration in the RRC connectionreconfiguration message, the UE sends an RRC connection reconfigurationcomplete message to the master base station, where the message is usedto indicate, to the master base station, that the UE completes thecorresponding configuration.

S308. The master base station sends a secondary base stationreconfiguration complete message to the secondary base station, wherethe message is used to indicate, to the secondary base station, that theUE completes the corresponding configuration.

S309. The UE and the secondary base station perform random access. Thereis no sequence between S309 and S307.

According to the information transmission method provided in thisembodiment, when initiating PDU session setup in a core network, themaster base station decides to split some or all flows to the secondarybase station, and sends identification information of the flows to thesecondary base station. The secondary base station determines QoSrequirements of the flows based on the identification information of theflows, and map the flows to a DRB that meets the QoS requirements of theflows, thereby implementing more refined QoS management on the flows.

FIG. 4 is a flowchart of an information transmission method according toyet another embodiment of this application. As shown in FIG. 4, themethod includes the following steps.

S401. A master base station decides, based on a load status and thelike, to transfer some or all flows to a secondary base station.

S402. The master base station sends a secondary base station additionrequest message to the secondary base station, where the message carriesat least one group of correspondence between a DRB and a flow, andinformation about the flow. Specifically, the correspondence may be thatone DRB ID is corresponding to at least one flow identifier. Theinformation about the flow includes a GTP tunnel identifier and atransport layer address of a PDU session to which the flow belongs on acore network node. Optionally, the information about the flow mayfurther include a QoS characteristic of the flow and/or an identifier ofthe PDU session to which the flow belongs.

S403. The secondary base station sends a secondary base station additionrequest reply message to the master base station. The message carriesinformation about a DRB corresponding to an admitted and split flow, andmay further carry information about a rejected DRB. Specifically, theinformation about the DRB corresponding to the split flow admitted bythe secondary base station may include an identifier of the DRB. Ifflows in the to DRB belong to only one PDU session, the informationabout the DRB further includes a GTP tunnel identifier and a transportlayer address of the PDU session to which the flows in the DRB belong onthe secondary base station. If flows in the DRB belong to different PDUsessions, the information about the DRB further includes an identifierof a flow, and a GTP tunnel identifier and a transport layer address ofa PDU session in which the flow is located on the secondary basestation. The information about the DRB rejected by the secondary basestation includes at least a DRB ID. The secondary base station may admitonly some flows in the DRB, and in this case, the information about therejected DRB further includes an identifier of a rejected flow.Optionally, flow information of two lists may further include anidentifier of a PDU session.

S404. The master base station sends an RRC connection reconfigurationmessage to UE. The message carries DRB configuration information of aflow split from the master base station to the secondary base station.Optionally, the configuration information further indicates anidentifier of a flow corresponding to a DRB.

S405. After completing configuration in the RRC connectionreconfiguration message, the UE sends an RRC connection reconfigurationcomplete message to the master base station, where the message is usedto indicate, to the master base station, that the UE completes thecorresponding configuration.

S406. The master base station sends a secondary base stationreconfiguration complete message to the secondary base station, wherethe message is used to indicate, to the secondary base station, that theUE completes the corresponding configuration.

S407. The UE and the secondary base station perform random access. Thereis no sequence between S407 and S405.

S408. The master base station sends a sequence number (SN) statustransfer message to the secondary base station. If the DRB isconfigured, the master base station needs to send a correspondingsending status of the DRB to the secondary base station. An SN numberwritten in the SN status transfer message may be a sequence number of apacket data convergence protocol (PDCP) and/or a sequence number of aflow.

S409. The master base station performs data forwarding. In this case, ifeach PDU session is corresponding to one tunnel between the master basestation and the secondary base station, a flow identifier needs to beadded to a header of a GTP field during data forwarding. A dashed linearrow in FIG. 4 indicates that S409 is an optional step.

S410. The master base station sends a session modification indicationmessage to a core network. The message is used to instruct an NGC totransfer a corresponding flow to the secondary base station. The messagecarries a QoS mark, and a GTP tunnel identifier and a transport layeraddress of the PDU session that carries the flow identified by the QoSmark on the secondary base station. Optionally, the message may furtherinclude an identifier of a PDU session to which the flow belongs.

If an entire PDU session is transferred to the secondary base station,in this case, the message may carry only an identifier of the PDUsession, and a GTP tunnel identifier and a transport layer address ofthe PDU session on the secondary base station. There is no sequencebetween S410 and S405.

S411. The core network sends a session modification confirmation messageto the master base station. The session modification confirmationmessage is used by the master base station to confirm the modification.S411 is an optional step.

It should be noted that, in this case, the core network may modify a GTPtunnel identifier and a transport layer address of a corresponding PDUsession on a core network node for the master base station or thesecondary base station. If the modification is performed for the masterbase station, a modified GTP tunnel identifier and transport layeraddress may be notified to the master base station by using the sessionmodification confirmation message. If the modification is performed forthe secondary base station, an indication message needs to beadditionally sent to the secondary base station, and a modified GTPtunnel identifier and transport layer address of the corresponding PDUsession on the core network node are notified to the secondary basestation. In this case, the message in S402 may not carry the GTP tunnelidentifier and the transport layer address of the PDU session on thecore network node.

According to the information transmission method provided in thisembodiment, after the core network and the master base station set up aPDU session, the master base station decides to split some or all flowsto the secondary base station, and sends identification information ofthe flows to the secondary base station. The secondary base station mapsthe flows to one or more DRBs that meets QoS requirements of the flows,thereby implementing more refined QoS management on the flows.

FIG. 5 is flowchart of an information transmission method according tostill another embodiment of this application. As shown in FIG. 5, themethod includes the following steps.

S501. UE determines a first DRB based on identification information offirst data.

S502. The UE sends the first data by using the first DRB.

In this embodiment, the first data is uplink data, the identificationinformation of the first data includes at least one piece of informationof a flow identifier (for example, a QoS mark) of the first data and anidentifier of a PDU session to which the first data belongs. The UEdetermines, based on the identification information of the first data, aDRB corresponding to the identification information, namely, the firstDRB. The first DRB may be a DRB carried by a master base station, or maybe a DRB carried by a secondary base station. A correspondence betweenthe identification information of the first data and the DRB may beinformation preconfigured in the UE, or may be information determined bythe UE based on a correspondence between a QoS mark of a flow indownlink data and a DRB, or may be information determined by the UE inanother manner.

Therefore, according to the information transmission method provided inthis embodiment, the UE may determine, based on a flow identifier ofuplink data and an identifier of a PDU session, a DRB that matches a QoSrequirement of the uplink data, and a bearer can be created andtransferred based on flow information.

Optionally, that UE determines a first DRB based on identificationinformation of a first data includes:

S503. The UE determines that a default bearer corresponding to anidentifier of a PDU session is the first DRB, where the identificationinformation of the first data includes the identifier of the PDUsession.

According to the information transmission method provided in thisembodiment, the default bearer may be on the master base station, or maybe on the secondary base station. The UE may determine the DRB thatmatches the QoS requirement of the uplink data without exchanginginformation with another network element, so that signaling overheadscan be reduced.

When sending the uplink data by using the default bearer, the UE sendsthe flow identifier corresponding to the uplink data to a base station.After receiving the uplink data sent by the UE by using the defaultbearer, the base station may perform mapping from a flow to a DRB foruplink data subsequently sent by the UE, and notify the UE of a mappingrelationship between a subsequently sent flow and a DRB. The DRB may bethe foregoing default bearer, or may be a new bearer.

Optionally, that UE determines a first DRB based on identificationinformation of first data includes:

S504. The UE sends a first request message to a base station, where thefirst request message includes the identification information of thefirst data, and the first request message is used to request the basestation to perform DRB mapping for the first data.

The performing DRB mapping for the first data includes: mapping thefirst data to another DRB than the default bearer. The another DRB maybe an existing DRB, or may be a newly created DRB. The another DRB maybe a DRB on the master base station, or may be a DRB on the secondarybase station.

S505. The UE receives a reply message from the base station, where thereply message includes a mapping relationship between the first data andthe first DRB.

According to the information transmission method provided in thisembodiment, the UE may send the first request message to the basestation (the master base station or the secondary base station), wherethe first request message includes at least one piece of information ofa QoS mark and an identifier of a PDU session. The first request messageis used to request the base station to perform DRB mapping for dataindicated by the QoS mark and the identifier of the PDU session.Therefore, the UE may determine the DRB that matches the QoS requirementof the uplink data, and a bearer can be created or transferred based onflow information.

Optionally, the method further includes:

S506. The UE determines the identification information of the first databased on upper layer information and non-access stratum (NAS)information.

An upper layer is an application layer of the UE, for example, anapplication program running on the UE. An access stratum (AS) of the UEmay determine the identification information of the first data based oninformation from the upper layer or a NAS. The identificationinformation of the first data includes the identifier of the PDU sessioncorresponding to the first data and the flow identifier (for example,the QoS mark) of the first data. The AS of the UE receives theidentifier of the PDU session from the upper layer, and the AS of the UEreceives the flow identifier of the first data from the NAS.

Specifically, the NAS of the UE may determine the QoS mark of the databased on a packet filter. The packet filter is a policy, and is used todetermine, from data that includes a plurality of characteristics, data,namely, a flow, that meets a specific rule.

The AS of the UE determines the DRB based on the identificationinformation of the first data. If the identification information of thefirst data has no corresponding DRB, the AS of the UE determines thedefault bearer based on the identifier of the PDU session, and sends thefirst flow by using the default bearer.

Therefore, according to the information transmission method provided inthis embodiment, the AS of the UE determines identification informationof the uplink data based on the upper layer information and the NASinformation, to determine, based on the identification information ofthe uplink data, the DRB for sending the uplink data.

The solutions provided in the embodiments are mainly described abovefrom a perspective of interaction between network elements. To implementthe foregoing functions, each network element includes a correspondinghardware structure and/or software module for executing the functions.In combination with the examples described in the embodiments disclosedin this specification, units, algorithms steps may be implemented byhardware or a combination of hardware and computer software in thisapplication. Whether a function is performed by hardware or hardwaredriven by computer software depends on particular applications anddesign constraints of the technical solutions. Different methods may beused to implement the described functions for each particularapplication, but it should not be considered that the implementationgoes beyond the scope of this application.

In the embodiments, functional unit division may be performed on themaster base station, the secondary base station, the core networkdevice, the UE, and the like based on the foregoing method examples. Forexample, each functional unit may be obtained through division based ona corresponding function, or two or more functions may be integratedinto one processing unit. The integrated unit may be implemented in aform of hardware, or may be implemented in a form of a softwarefunctional unit. It should be noted that the unit division in theembodiments is an example, and is merely logical function division andmay be another division manner during actual implementation.

When an integrated unit is used, FIG. 6 is a schematic block diagram ofa master base station in the foregoing embodiments. A master basestation 600 includes a processing unit 602 and a communication unit 603.The processing unit 602 is configured to control and manage an action ofthe master base station 600. For example, the processing unit 602 isconfigured to support, by using the communication unit 603, the masterbase station 600 in performing S201, S303, S402, and other processesused to perform the technologies described in this specification. Thecommunication unit 603 is configured to support communication betweenthe master base station 600 and another network entity, for example,communication with a secondary base station, a core network device, andUE shown in FIG. 2. The master base station 600 may further include astorage unit 601, configured to store program code and data of themaster base station 600.

The processing unit 602 may be a processor or a controller, such as acentral processing unit (CPU), a general-purpose processor, a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a field programmable gate array (FPGA), or another programmablelogical device, a transistor logical device, a hardware component, or acombination thereof. The controller/processor may implement or executevarious example logical blocks, modules, and circuits described withreference to content disclosed in this application. Alternatively, theprocessor may be a combination of processors implementing a computingfunction, for example, a combination of one or more microprocessors, ora combination of the DSP and a microprocessor. The communication unit603 may be a communication interface, a transceiver, or the like. Thestorage unit 601 may be a memory.

When the processing unit 602 is the processor, the communication unit603 is the communication interface and the transceiver, and the storageunit 601 is the memory, the master base station in this embodiment maybe a master base station shown in FIG. 7.

Referring to FIG. 7, the master base station 610 includes a processor612, a communication interface 613, a transceiver 614, and a memory 611.The communication interface 613, the transceiver 614, the processor 612,and the memory 611 may communicate with each other by using an internalconnection path, and transmit a control signal and/or a data signal. Thecommunication interface 613 may be configured to communicate with a corenetwork device. The transceiver 614 may be configured to communicatewith UE.

For the purpose of convenient and brief description, for a detailedworking process of the foregoing apparatus or unit in the master basestation 610, refer to a corresponding process in the foregoing methodembodiments. Details are not described herein again.

The master base station provided in this embodiment sends identificationinformation of a flow to a secondary base station. The secondary basestation determines a QoS requirement of the flow based on theidentification information of the flow, and maps the flow to a DRB thatmeets the QoS requirement of the flow, thereby implementing more refinedQoS management on data.

When an integrated unit is used, FIG. 8 is a schematic block diagram ofa secondary base station in the foregoing embodiments. A secondary basestation 700 includes a processing unit 702 and a communication unit 703.The processing unit 702 is configured to control and manage an action ofthe secondary base station 700. For example, the processing unit 702 isconfigured to support, by using the communication unit 703, thesecondary base station 700 in performing S202, S304, S403, and otherprocesses used to perform the technologies described in thisspecification. The communication unit 703 is configured to supportcommunication between the secondary base station 700 and another networkentity, for example, communication with a master base station, a corenetwork device, and UE shown in FIG. 2. The secondary base station 700may further include a storage unit 701, configured to store program codeand data of the secondary base station 700.

The processing unit 702 may be a processor or a controller, for example,may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA oranother programming logical device, a transistor logic device, ahardware component, or any combination thereof. The controller/processormay implement or execute various example logical blocks, modules, andcircuits described with reference to content disclosed in thisapplication. Alternatively, the processor may be a combination ofprocessors implementing a computing function, for example, a combinationof one or more microprocessors, or a combination of the DSP and amicroprocessor. The communication unit 703 may be a communicationinterface, a transceiver, or the like. The storage unit 701 may be amemory.

When the processing unit 702 is the processor, the communication unit703 is the communication interface and the transceiver, and the storageunit 701 is the memory, the secondary base station in this embodimentmay be a secondary base station shown in FIG. 9.

Referring to FIG. 9, the secondary base station 710 includes a processor712, a communication interface 713, a transceiver 714, and a memory 711.The communication interface 713, the transceiver 714, the processor 712,and the memory 711 may communicate with each other by using an internalconnection path, and transmit a control signal and/or a data signal. Thecommunication interface 713 may be configured to communicate with a corenetwork device. The transceiver 714 may be configured to communicatewith UE.

For the purpose of convenient and brief description, for a detailedworking process of the foregoing apparatus or unit in the secondary basestation 710, refer to a corresponding process in the foregoing methodembodiments. Details are not described herein again.

The secondary base station provided in this embodiment receivesidentification information of a flow sent by a master base station, todetermine a QoS requirement of the flow based on the identificationinformation of the flow, and map the flow to a DRB that meets the QoSrequirement of the flow, thereby implementing more refined QoSmanagement on data.

When an integrated unit is used, FIG. 10 is a simplified structuraldiagram of a core network device in the foregoing embodiments. A corenetwork device 800 includes a processing unit 802 and a communicationunit 803. The processing unit 802 is configured to control and manage anaction of the core network device 800. For example, the processing unit802 is configured to support, by using the communication unit 803, thecore network device 800 in performing receiving processes correspondingto S203 and S204 and other processes used to perform the technologiesdescribed in this specification. The communication unit 803 isconfigured to support communication between the core network device 800and another network entity, for example, communication with a masterbase station and a secondary base station shown in FIG. 2. The corenetwork device 800 may further include a storage unit 801, configured tostore program code and data of the core network device 800.

The processing unit 802 may be a processor or a controller, for example,may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA oranother programming logical device, a transistor logic device, ahardware component, or any combination thereof. The controller/processormay implement or execute various example logical blocks, modules, andcircuits described with reference to content disclosed in thisapplication. Alternatively, the processor may be a combination ofprocessors implementing a computing function, for example, a combinationof one or more microprocessors, or a combination of the DSP and amicroprocessor. The communication unit 803 may be a communicationinterface, or the like. The storage unit 801 may be a memory.

When the processing unit 802 is the processor, the communication unit803 is the communication interface, and the storage unit 801 is thememory, the core network device in this embodiment may be a core networkdevice shown in FIG. 11.

Referring to FIG. 11, the core network device 810 includes a processor812, a communication interface 813, and a memory 811. The communicationinterface 813, the processor 812, and the memory 811 may communicatewith each other by using an internal connection path, and transmit acontrol signal and/or a data signal. The communication interface 813 maybe configured to communicate with a master base station and a secondarybase station.

For the purpose of convenient and brief description, for a detailedworking process of the foregoing apparatus or unit in the core networkdevice 810, refer to a corresponding process in the foregoing methodembodiments. Details are not described herein again.

The core network device provided in this embodiment sends flows to themaster base station and the secondary base station based on tunnelendpoint information corresponding to flows on the master base stationand tunnel endpoint information corresponding to flows on the secondarybase station. The two pieces of tunnel endpoint information are receivedfrom the master base station. Based on tunnel endpoint information thatis received from the master base station and that is corresponding to aflow migrated to the secondary base station on the secondary basestation, a bearer can be created and transferred based on flowinformation.

When an integrated unit is used, FIG. 12 is a block diagram of a UE inthe foregoing embodiments. UE 900 includes a processing unit 902 and acommunication unit 903. The processing unit 902 is configured to controland manage an action of the UE 900. For example, the processing unit 902is configured to support, by using the communication unit 903, the UE900 in performing S501 and S502 and other processes used to perform thetechnologies described in this specification. The communication unit 903is configured to support communication between the UE 900 and anothernetwork entity, for example, communication with a master base stationand a secondary base station shown in FIG. 2. The UE 900 may furtherinclude a storage unit 901, configured to store program code and data ofthe UE 900.

The processing unit 902 may be a processor or a controller, for example,may be a CPU, a general-purpose processor, a DSP, an ASIC, an FPGA oranother programming logical device, a transistor logic device, ahardware component, or any combination thereof. The controller/processormay implement or execute various example logical blocks, modules, andcircuits described with reference to content disclosed in thisapplication. Alternatively, the processor may be a combination ofprocessors implementing a computing function, for example, a combinationof one or more microprocessors, or a combination of the DSP and amicroprocessor. The communication unit 903 may be a transceiver, or thelike. The storage unit 901 may be a memory.

When the processing unit 902 is the processor, the communication unit903 is the transceiver, and the storage unit 901 is the memory, the UEin this embodiment may be UE shown in FIG. 13.

Referring to FIG. 13, the UE 910 includes a processor 912, a transceiver913, and a memory 911. The transceiver 913, the processor 912, and thememory 911 may communicate with each other by using an internalconnection path, and transmit a control signal and/or a data signal. Thetransceiver 913 may be configured to communicate with a master basestation and a secondary base station.

For the purpose of convenient and brief description, for a detailedworking process of the foregoing apparatus or unit in the UE 910, referto a corresponding process in the foregoing method embodiments. Detailsare not described herein again.

Therefore, the UE provided in this embodiment may determine, based onidentification information of a flow to which to-be-sent data belongs, aDRB that matches a QoS requirement of the data, and a bearer can becreated and transferred based on flow information.

It should be understood that sequence numbers of the foregoing processesdo not mean execution sequences in various embodiments of thisapplication. The execution sequences of the processes should bedetermined based on functions and internal logic of the processes, andshould not be construed as any limitation on the implementationprocesses of the embodiments.

In addition, the term “and/or” in this specification describes only anassociation relationship for describing associated objects andrepresents that three relationships may exist. For example, A and/or Bmay represent the following three cases: Only A exists, both A and Bexist, and only B exists. In addition, the character “/” in thisspecification generally indicates an “or” relationship between theassociated objects.

All or some of the foregoing embodiments may be implemented throughsoftware, hardware, firmware, or any combination thereof. When softwareis used to implement the embodiments, the embodiments may be all orpartially implemented in a form of a computer program product. Thecomputer program product includes one or more computer instructions.When the computer program instructions are loaded and executed on thecomputer, the procedure or functions according to this application areall or partially generated. The computer may be a general-purposecomputer, a dedicated computer, a computer network, or otherprogrammable apparatuses. The computer instructions may be stored in acomputer readable storage medium or may be transmitted from a computerreadable storage medium to another computer readable storage medium. Forexample, the computer instructions may be transmitted from a web site,computer, server, or data center to another web site, computer, server,or data center in a wired (for example, a coaxial cable, an opticalfiber, or a digital subscriber line (DSL)) or wireless (for example,infrared, radio, or microwave) manner. The computer readable storagemedium may be any usable medium accessible by a computer, or a datastorage device, such as a server or a data center, integrating one ormore usable media. The usable medium may be a magnetic medium (forexample, a floppy disk, a hard disk, or a magnetic tape), an opticalmedium (for example, a DVD), a semiconductor medium (for example, asolid state disk (SSD)), or the like.

The objectives, technical solutions, and benefits of this applicationare further described in detail in the foregoing specificimplementations. It should be understood that the foregoing descriptionsare merely specific implementations of this application, but are notintended to limit the protection scope of this application. Anymodification, equivalent replacement, or improvement made based on thetechnical solutions of this application shall fall within the protectionscope of this application.

What is claimed is:
 1. A communication system, comprising: a masternetwork node, a secondary network node, and a core network device,wherein the core network device is configured to perform flowtransmission with the master network node or the secondary network node;the master network node is configured to send a first message to thesecondary network node for allocating transmission resources for one ormore flows to be transmitted between the secondary network node and aterminal device, wherein the first message carries identificationinformation of each of the one or more flows to be transmitted, and anidentifier list of one or more data radio bearers (DRBs) available tothe secondary network node; the secondary network node is configured todetermine whether to admit or reject each of the one or more flowsindicated in the first message, and send a response message in responseto the first message to the master network node; the secondary networknode is further configured to determine a mapping relationship betweenone or more flows admitted by the secondary network node and a dataradio bearer (DRB) whose identifier is indicated by the identifier listfor transmitting the one or more flows admitted by the secondary networknode via the DRB; the master network node is further configured to senda second message comprising DRB configuration information to theterminal device, receive a response to the second message from theterminal device, and send a third message to the secondary network node,indicating that a DRB for each flow admitted by the secondary networknode is configured according to the DRB configuration information by theterminal device; wherein the DRB configuration information comprises atleast one of: DRB configuration information of the secondary networknode, or DRB configuration information of the master network node; theDRB configuration information of the secondary network node comprisesidentification information of the one or more flows admitted by thesecondary network node, and the identifier of the DRB mapped with theone or more flows admitted by the secondary network node; and the DRBconfiguration information of the master network node comprisesidentification information of one or more flows transmitted between themaster network node and the terminal device, and identifiers of one ormore DRBs mapped with the one or more flows transmitted between themaster network node and the terminal device.
 2. The system according toclaim 1, wherein the DRB configuration information of the secondarynetwork node further comprises an identifier of a Protocol Data Unit(PDU) session to which the flows admitted by the secondary network nodebelong.
 3. The system according to claim 1, wherein the DRBconfiguration information of the master network node further comprisesan identifier of a second Protocol Data Unit (PDU) session to which theflows transmitted between the master network node and the terminaldevice belong.
 4. The system according to claim 1, wherein a ProtocolData Unit (PDU) session to which the flows admitted by the secondarynetwork node belong is same as a PDU session to which the flowstransmitted between the master network node and the terminal devicebelong.
 5. The system according to claim 1, further comprising a secondcore network device, wherein the second core network device isconfigured to receive, from the master network node, identificationinformation of a flow admitted by the secondary network node, and tunnelendpoint information corresponding to the flow admitted by the secondarynetwork node.
 6. The system according to claim 5, wherein the secondcore network device is further configured to receive, from the masternetwork node, identification information of a flow admitted by themaster network node, and tunnel endpoint information corresponding tothe flow admitted by the master network node.
 7. The system according toclaim 1, wherein the response message in response to the first messagecomprises identification information of a flow admitted by the secondarynetwork node and tunnel endpoint information corresponding to theadmitted flow, or a flow rejected by the secondary network node.
 8. Thesystem according to claim 1, further comprising a second core networkdevice, wherein the master network node is further configured to receivea session establishment request message from a second core networkdevice, and determine to transfer some or all flows indicated by thesession establishment request message to the secondary network node fortransmission.
 9. An apparatus implemented in a master network node,comprising a processor and a memory storing program instructions;wherein the instructions, when executed by the processor, cause themaster network node to: send a first message to a secondary network nodefor allocating transmission resources for one or more flows to betransmitted between the secondary network node and a terminal device,wherein the first message carries identification information of each ofthe one or more flows to be transmitted, and an identifier list of oneor more data radio bearers (DRBs) available to the secondary networknode, and the identification information and the identifier list areused for the secondary network node to determine a mapping relationshipbetween one or more flows admitted by the secondary network node and adata radio bearer (DRB) whose identifier is indicated by the identifierlist for transmitting the one or more flows admitted by the secondarynetwork node via the DRB; receive, from the secondary network node, aresponse to the first message; send a second message comprising DRBconfiguration information to the terminal device; receive a response tothe second message from the terminal device; and send a third message tothe secondary network node, indicating that a DRB for each flow admittedby the secondary network node is configured according to the DRBconfiguration information by the terminal device; wherein the DRBconfiguration information comprises at least one of: DRB configurationinformation of the secondary network node, or DRB configurationinformation of the master network node; the DRB configurationinformation of the secondary network node comprises identificationinformation of the one or more flows admitted by the secondary networknode, and the identifier of the DRB mapped with the one or more flowsadmitted by the secondary network node; and the DRB configurationinformation of the master network node comprises identificationinformation of one or more flows transmitted between the master networknode and the terminal device, and identifiers of one or more DRBs mappedwith the one or more flows transmitted between the master network nodeand the terminal device.
 10. The apparatus according to claim 9, whereinthe DRB configuration information of the secondary network node furthercomprises an identifier of a Protocol Data Unit (PDU) session to whichthe flows admitted by the secondary network node belong.
 11. Theapparatus according to claim 9, wherein the DRB configurationinformation of the master network node further comprises an identifierof a second Protocol Data Unit (PDU) session to which the flowstransmitted between the master network node and the terminal devicebelong.
 12. The apparatus according to claim 9, wherein a Protocol DataUnit (PDU) session to which the flows admitted by the secondary networknode belong is same as a PDU session to which the flows transmittedbetween the master network node and the terminal device belong.
 13. Theapparatus according to claim 9, wherein the instructions, when executedby the processor, further cause the master network node to: send, to acore network device, identification information of a flow admitted bythe secondary network node, and tunnel endpoint informationcorresponding to the flow admitted by the secondary network node. 14.The apparatus according to claim 13, wherein the instructions, whenexecuted by the processor, further cause the master network node to:send, to the core network device, identification information of a flowadmitted by the master network node, and tunnel endpoint informationcorresponding to the flow admitted by the master network node.
 15. Theapparatus according to claim 9, wherein the response to the firstmessage comprises identification information of a flow admitted by thesecondary network node and tunnel endpoint information corresponding tothe flow; or a flow rejected by the secondary network node.
 16. Theapparatus according to claim 9, wherein the instructions, when executedby the processor, further cause the master network node to: add a flowidentifier to a header of a general packet radio service (GPRS)tunneling protocol (GTP) field of a data packet for performing dataforwarding to the secondary network node.
 17. The apparatus according toclaim 9, wherein the instructions, when executed by the processor,further cause the master network node to: receive a sessionestablishment request message from a second core network device, anddetermine to transfer some or all flows indicated by the sessionestablishment request message to the secondary network node fortransmission.
 18. An apparatus implemented in a terminal device,comprising a processor and a memory storing program instructions;wherein the instructions, when executed by the processor, cause theterminal device to: receive a message from a master network node,wherein the message comprises data radio bearer (DRB) configurationinformation; configure a DRB for data transmission with the masternetwork node or a secondary network node according to the DRBconfiguration information; and send a response to the message to themaster network node, indicating that the DRB has been configured;wherein the DRB configuration information comprises DRB configurationinformation of the secondary network node, or, DRB configurationinformation of the master network node and DRB configuration informationof the secondary network node; the DRB configuration information of thesecondary network node comprises identification information of one ormore flows admitted by the secondary network node to transmit betweenthe terminal device and the secondary network node, and an identifier ofa DRB mapped with the one or more flows admitted by the secondarynetwork node; and the DRB configuration information of the masternetwork node comprises identification information of one or more flowstransmitted between the master network node and the terminal device, andidentifiers of one or more DRBs mapped with the one or more flowstransmitted between the master network node and the terminal device;wherein a mapping relationship between the identifier of the DRB and theone or more flows admitted by the secondary network node is determinedby the secondary network node according to identification information ofone or more flows to be transmitted between the secondary network nodeand the terminal device, and an identifier list of one or more DRBsavailable to the secondary network node, wherein the identifier of theDRB is indicated by the identifier list.
 19. The apparatus according toclaim 18, wherein the DRB configuration information of the secondarynetwork node further comprises an identifier of a Protocol Data Unit(PDU) session to which the flows admitted by the secondary network nodebelong.
 20. The apparatus according to claim 18, wherein the DRBconfiguration information of the master network node further comprisesan identifier of a Protocol Data Unit (PDU) session to which the flowstransmitted between the master network node and the terminal devicebelong.
 21. The apparatus according to claim 18, wherein a Protocol DataUnit (PDU) session to which the flows admitted by the secondary networknode belong is same as a PDU session to which the flows transmittedbetween the master network node and the terminal device belong.
 22. Theapparatus according to claim 18, wherein the instructions, when executedby the processor, further cause the terminal device to: send uplink datavia a default DRB corresponding to a Protocol Data Unit (PDU) session;wherein the PDU session is established between the master network nodeand a core network device, or between the secondary network node and thecore network device, or between the core network device and both themater network node and the secondary network node.